-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Go backend; modify backend request pattern. #235
Conversation
…erData, createSketch.
pid={ | ||
Array.from(this.props.programs)[this.state.selectedKey] | ||
? Array.from(this.props.programs)[this.state.selectedKey].uid | ||
: "" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a huge fan of how I made the changes to this file, but these felt the most natural without modifying much else. Thoughts?
I'll give a more formal review after I finish my final, but just some quick notes:
I think it would probably be wise to incrementally implement these changes, i.e. allow |
I'm not opposed to simply basing my changes directly off of the
Will do.
Here's the props I have added with brief descriptions:
|
Superseded by #253. |
Ahoy! This is a PR to switch out our backends from JS to Go. Here's a breakdown of the changes:
fetch.js
.ok
field.mostRecentProgramID
prop to the Main component.updateProgram
behaviordeleteProgram
call to use both user ID and program ID (uid, pid) for program deletion instead of the old uid, docID, and name system.pid
prop inConfirmDeleteModal
, which is used when the modal makes the call to the backend.updateUserData
calls slightly (everything is sent as an object).sketchCount
prop to ourCreateSketchModal
used when creating a new sketch.This PR is presently blocked on account of this PR which updates the Go backend to work with the frontend changes made here. I'll unblock it on merge of said PR.
Stay healthy everyone and have a great spring break!